Data exchange schemas

ABSTRACT

Various systems, mediums, and methods herein describe aspects of data exchange schemas accessible with client devices over communication networks in data infrastructures. A data exchange system may build one or more data exchange schemas for a user. The system may also determine a location of a client device of the user associated with one or more entities. Based on the location of the client device, the system may identify a data exchange schema of the user for transferring data to the one or more entities. The system may determine an access for the one or more entities to a portion of data from the data exchange schema of the user. The system may also transmit a notification to the client device that indicates the access of the one or more entities to the portion of data from the data exchange schema.

TECHNICAL FIELD

This disclosure generally relates to data exchange schemas accessible byvarious devices over one or more communication networks.

BACKGROUND

With the advent of modern technology, users are increasinglytransferring their data to various entities over one or morecommunication networks. For example, a user may be able to utilize theirsmartphone to provide their name, address, and/or telephone number tonumerous entities over various communication networks efficiently,possibly within seconds. As such, various advancements to mobiletechnology and the data infrastructure have enabled the user toaccomplish such tasks without major technical difficulties and/orcomplications. Yet, with such conveniences provided with thesetechnological advancements, a number of drawbacks may emerge as well.

In various circumstances, users may have difficulties managing theirdata. For example, the user described above may have difficulty trackingwhich entities have their data, particularly their name, address,telephone number, and/or other types of data of the user. In particular,the user may find it challenging to remember prior instances where theuser may have transferred their data to a number of such entities.Further, these challenges may be further experienced based on the userproviding data to various such entities over longer periods of time,such as a number of years. Thus, the user may be left withoutrecognizing which entities may have their data, what types of data theentities may have accumulated from the user over the years, and/or howthe data may be used by such entities, among other possibleuncertainties.

As demonstrated in the scenario above, there is much need fortechnological advancements to support the management of data with theutilization of various aspects of mobile technology and the capabilitiesof the data infrastructure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an exemplary system, according to anembodiment;

FIG. 1B is a block diagram of another exemplary system, according to anembodiment;

FIG. 2A illustrates an exemplary system configured to support a set oftrays, according to an embodiment;

FIG. 2B illustrates an exemplary tray configured to support one or morecomponents, according to an embodiment;

FIG. 3A illustrates a data exchange system, according to an embodiment;

FIG. 3B illustrates a data exchange system with another entity,according to an embodiment;

FIG. 3C illustrates a data exchange system with yet another entity,according to an embodiment;

FIG. 4A illustrates an exemplary system with a client device, accordingto an embodiment;

FIG. 4B illustrates an exemplary system with a client device, accordingto an embodiment;

FIG. 4C illustrates an exemplary system with a client device, accordingto an embodiment;

FIG. 5 illustrates an exemplary method, according to an embodiment;

FIG. 6 illustrates an exemplary system with a client device, accordingto an embodiment; and

FIG. 7 illustrates an exemplary wearable computing device, according toan embodiment.

Embodiments of the present disclosure and their advantages may beunderstood by referring to the detailed description herein. It should beappreciated that reference numerals may be used to illustrate variouselements and features provided in the figures. Further, the figures mayillustrate various examples for purposes of illustration and explanationrelated to the embodiments of the present disclosure and not forpurposes of any limitation.

DETAILED DESCRIPTION

In some embodiments, a data exchange system may be configured to performoperations related to data anonymization, particularly to protectvarious privacy interests of a user. In particular, the data exchangesystem may manage user data in a number of data exchange schemas. Insome instances, the data exchange schemas may include secure databasesconfigured to maintain, manage, and/or organize data for a user,possibly based on the various types of data recognized by the system.Notably, the data exchange system may also manage the data exchangeschemas with or without user inputs to optimize the anonymization of theuser data. As such, the data exchange system may compile various typesof data associated with a user in a number of data exchange schemas.

In practice, for example, consider a scenario where a user visits adoctor's office. For illustrative purposes, further consider that theuser carries a smartphone and the data exchange system identifies theuser's location at the doctor's office, possibly based on retrieving thesmartphone's global positioning system (GPS) data over the network. Assuch, the system may identify a particular data exchange schema, such asan Extensible Markup Language (XML) schema, associated with the uservisiting the doctor's office. In particular, the system may identify theparticular schema from a number of different schemas developed for theuser. For example, there may be a data exchange schema associated withthe user going to a store, such as a grocery store, a clothing store, ahardware store, a restaurant, and/or the user's school, among otherpossible locations where data may be exchanged or transferred with theuser.

In some instances, the data exchange system may search for data in theone or more data exchange schemas identified. For example, consideringthe scenario above with the doctor's office, the system may search fordata indicating the user's name, address, birthdate, age, gender,height, weight, temperature, blood pressure, allergies, medical cardinformation or other health information, medical history,medications/prescriptions taken, and/or other forms of data related tothe user visiting the doctor's office. As such, the system may provideor display such data on the smartphone, possibly to allow the user tochange the data. For example, the user may add a number of symptoms theuser may have at the present time, which may be the basis for the visitto the doctor's office. Thus, the data may be provided to the doctor'soffice in one or more formats that the office may prefer. Notably, theuser is not required to fill out any forms, answer questions, and/ortake part in conventional practices that may be time consuming orinconvenient under the circumstances.

In some embodiments, the data exchange system provides an access to thedata described above in the one or more particular data exchangeschemas. In some instances, the access may be a limited access to thedata, possibly based on a number of controls and/or rules identified bythe system. For example, the system may send an electronic message(e.g., an email and/or a short message service (SMS) message) to thedoctor's office with a link to the data. Yet, the link may expire aftera given time period set based on the system detecting the smartphone'slocation to be at the doctor's office. Further, in some instances, thesystem may send the data to the doctor's office and then retrieve and/orremove the data from the databases of the doctor's office based ondetecting the user has left the doctor's office. For example, the systemmay remove the data from the doctor's databases to help ensure that theuser remains anonymous from other entities that may be interested in theuser's data. As such, the doctor's office may be prevented fromtransferring the data to other entities for purposes other than thoserelated to the medical interests of the user.

As noted, the data exchange schemas may be determined, created, and/ordeveloped for the user with and/or without the user's inputs. Forexample, the data exchange system may create a given data exchangeschema based on recognizing data transfers previously authorized by theuser. In one scenario, the system may identify that the user gets a cupof coffee at a given coffee shop regularly, such as on Monday mornings.As such, the system may give the coffee shop a limited access to theuser's account data when the user goes to the coffee shop to get a cupof coffee. Thus, the user may be able to get a cup of coffee without acredit card, for example. Yet, the system may also send a notificationto the user's smartphone requiring an input from the user to authorizethe coffee shop to have the limited access to the user's account todeduct a given amount from the user's balance to pay for the coffee. Assuch, the system may build data exchange schemas for the user based onrecognizing previous data transfers of the user. Further, the system mayalso build or modify the data exchange schemas based on inputs receivedfrom the user via the smartphone.

In some embodiments, the data exchange system may also record, track,and/or maintain records of the data provided to various entities.Particularly, in view of the various difficulties users face withtracking which entities have their data as described above, the dataexchange system may resolve such challenges. For example, the system mayrecord each instance where data is provided to a given entity, amongnumerous entities that may receive the data. By tracking and/ormaintaining such records, the user may view the various entities thatmay be in possession of their data. For example, the user may view suchrecords on their smartphone to determine which entities have access orpossession of their name, birthdate, and/or address, among other formsof data associated with the user.

In some embodiments, the access that an entity has to the user's datamay be controlled by the data exchange system and/or based on one ormore user inputs. In addition to implementing limited accesses asdescribed above, the system may create access rules that define theaccess that an entity has to the user's data. For example, an accessrule may involve the entity having access to the user's data forspecific purposes, such as the user's medical purposes or possibly forthe mere purpose of getting a cup of coffee, as described above.Further, an access rule may involve the entity being restricted fromtransferring the user's data to other entities. In particular, an accessrule may prevent the entity from saving the user's data to a remoteserver or computer. For example, the access rule may be implemented witha number of cryptographic protocols that may be used to encrypt theuser's data, possibly based on an entity attempting to save the user'sdata on a remote computer. As such, the user, possibly in possession ofthe encryption key, may be able to control when the data is unencryptedsuch that a particular entity may be able to view the data. Evenfurther, the data may be automatically encrypted once the entity hasviewed the data, possibly after one or more periods of time.

In some embodiments, the data exchange system may provide suggestions tothe user. For example, the system may inform the user that a particularentity has the user's address and phone number. Further, the system mayinform the user that the entity may have an incentive to provide theuser's address and phone number to other entities, possibly entitiesthat may not be authorized by the user to have the user's address andphone number. As such, the system may provide a suggestion to the userto create a rule with the particular entity's access to the user'saddress and/or phone number. For example, the system may provide asuggestion to limit and/or remove the entity's access to the user'saddress and phone number. In particular, based on one or more userinputs received by the user's smartphone, the system may limit theaccess of the entity to prevent the particular entity from transferringthe user's data to other entities, possibly utilizing one or moreencryption protocols described above.

It should be noted that the data exchange system may also dynamicallychange the data exchange schemas based on a number of factors. Forexample, the system may change data in a particular schema thatindicates the user's address, possibly to refresh the entities that mayhave access to the user's address. In practice, for instance, the systemmay recognize that the user has moved to a new address, possibly basedon one or more user inputs or data transferred to a mail carrierwebsite, a postal service website, and/or a digital address form, amongother possibilities. As such, the system may dynamically change theuser's address in an appropriate data exchange schema accordingly. Assuch, the user's new address may be transmitted, pushed out, and/ordistributed to select entities (e.g., a credit card entity, atelecommunications entity, a cable network entity, etc.) to inform suchentities of the user's new address. Notably, various inconveniencesinvolved with the user manually updating the user's address with each ofsuch entities may be eliminated accordingly.

Thus, the example embodiments described herein may resolve variouschallenges with managing data with mobile devices over communicationnetworks in variable data infrastructures. As such, the exampleembodiments described herein may resolve problems that did not existbefore the availability of the computer networks and/or the Internet. Inparticular, such embodiments may address problems specific to dataexchanges with the use of computer networks in such data infrastructuresand/or the Internet. Various such embodiments may provide solutions thatare technical nature and/or rooted in data management systems associatedwith mobile devices and aspects of the data infrastructure. Further,such embodiments may provide unconventional steps confined to one ormore particular useful applications related to maintaining data for agiven user, possibly to manage personal data for the user.

FIG. 1A is a block diagram of an exemplary system 100, according to anembodiment. The system 100, possibly referred to as the datainfrastructure 100, may be configured to transfer data over one or morecommunication networks 108. In particular, the system 100 may includethe server 102, possibly referred to as the server system 102. Theserver 102 may be configured to perform operations of a serviceprovider, such as PayPal, Inc. of San Jose, Calif., USA. Further, thesystem 100 may also include client device 104 and/or the client device106 operated by their respective users. In practice, the server 102 andthe client devices 104 and/or 106 may be configured to communicate overthe one or more communication networks 108.

The system 100 may operate with more or less than the computing devicesshown in FIG. 1A, where each device may be configured to communicateover one or more communication networks 108, possibly to transfer dataaccordingly. The one or more communication networks 108 may also includea packet-switched network configured to provide digital networkingcommunications, possibly to exchange data of various forms, content,type, and/or structure. The one or more communication networks 108 mayinclude a data network such as a private network, a local area network,and/or a wide area network. In some instances, the one or morecommunication networks 108 may include a communications network such asa telecommunications network and/or a cellular network with one or morebase stations, among other possible networks.

The data/data packets 122 and/or 124 may be transferrable usingcommunication protocols such as packet layer protocols, packet ensembleprotocols, and/or network layer protocols. For example, the data/datapackets 122 and/or 124 may be transferrable using transmission controlprotocols and/or internet protocols (TCP/IP). In various embodiments,each of the data/data packets 122 and 124 may be assembled ordisassembled into larger or smaller packets of varying sizes, such assizes from 1,000 to 1,500 bytes, for example, among other possiblesizes. As such, data/data packets 122 and/or 124 may be transferrableover the one or more networks 108 and to various locations in the datainfrastructure 100.

In some embodiments, the server 102 may take a variety of forms. Theserver 102 may be an enterprise server, possibly configured with one ormore operating systems to facilitate the scalability of the datainfrastructure 100. For example, the server 102 may configured with aUnix-based operating system to integrate with a growing number of otherservers, client devices 104 and/or 106, and one or more networks 108over the system architecture 100. The server 102 may further facilitateworkloads associated with numerous data transfers in view of anincreasing number of data exchange schemas implemented for users.

In some embodiments, the server 102 may include multiple components,such as a hardware processor 112, a non-transitory memory 114, anon-transitory data storage 116, and/or a communication interface 118,among other possible components, any of which may be communicativelylinked via a system bus, network, or other connection mechanism 120. Thehardware processor 112 may take the form of a multi-purpose processor, amicroprocessor, a special purpose processor, a digital signal processor(DSP) and/or other types of processing components. For example, theprocessor 112 may include an application specific integrated circuit(ASIC), a programmable system-on-chip (SOC), and/or a field-programmablegate array (FPGA) to process, read, and/or write data for an increasingnumber of data exchange schemas for numerous users. In particular, theprocessor 112 may include a variable-bit (e.g., 64-bit) processorarchitecture specifically configured to facilitate the scalability ofthe increasing number of data exchange schemas. As such, the one or moreprocessors 112 may execute varying instructions sets (e.g., simplifiedand complex instructions sets) with fewer cycles per instruction thanother conventional general-purpose processors to improve the performanceof the server 102 for purposes of scalability and/or the accommodationof growth.

In practice, for example, the hardware processor 112 may be configuredto parse the one or more data packets 122 to identify one or more typesof data (e.g., data entries) transferred with the client device 104. Theprocessor 112 may also create one or more data exchange schemas for auser of the client device 104 based on the one or more types of datatransferred. As such, possibly based on a location of the client device104 associated with an entity, e.g., the doctor's office or a coffeeshop, the processor 112 may identify a particular data exchange schemathat corresponds to the entity. For example, the processor 112 maydetermine an access of the entity to a portion of the data from theparticular data exchange schema. The processor 112 may also initiate thetransmittal of a notification to the client device 104 of the user thatindicates the access the entity to the portion of data.

The non-transitory memory component 114 and/or the non-transitory datastorage 116 may include one or more volatile, non-volatile, and/orreplaceable data storage components, such as a magnetic, optical, and/orflash storage that may be integrated in whole or in part with thehardware processor or component 112. Further, the memory component 114may include a number of instructions and/or instruction sets. Theprocessing component 112 may be coupled to the memory component 114 andconfigured to read the instructions to cause the server 102 to performoperations, such as those described in this disclosure, illustrated bythe accompanying figures, and/or otherwise contemplated herein.

The communication interface or component 118 may take a variety offont's and may be configured to allow the server 102 to communicate withone or more devices, such as the client devices 104 and/or 106. Forexample, the communication interface 118 may include a transceiver thatenables the server 102 to communicate with the client devices 104 and/or106 via the one or more communication networks 108. Further, thecommunication interface 118 may include a wired interface, such as anEthernet interface, to communicate with the client devices 104 and/or106. Yet further, the communication interface 118 may include a wirelessinterface, such as a cellular interface, a Global System for MobileCommunications (GSM) interface, a Code Division Multiple Access (CDMA)interface, and/or a Time Division Multiple Access (TDMA) interface,among other possibilities. In addition, the communication interface 118may include a wireless local area network interface such as a WI-FIinterface configured to communicate with a number of differentprotocols. As such, the communication interface 118 may include awireless interface configured to transfer data over short distancesutilizing short-wavelength radio waves in approximately the 2.4 to 2.485GHz range. In some instances, the communication interface 118 maysend/receive data or data packets 122 and/or 124 to/from client devices104 and/or 106.

The client devices 104 and 106 may also be configured to perform avariety of operations such as those described in this disclosure,illustrated by the accompanying figures, and/or otherwise contemplatedherein. For example, the client devices 104 and 106 may be configured totransfer data packets 122 and/or 124 with the server 102, such that theserver 102 may manage one or more data exchange schemas for respectiveusers of the client device 104 and/or 106. The server 102 may manage thedata exchange schemas based on various types of data transferred withthe data packets 122 and/or 124. For example, the server 102 maydetermine data exchange schemas based on the data/data packets 122and/or 124 including location data, such as Global Positioning System(GPS) data or GPS coordinate data, triangulation data, beacon data,WI-FI data, peer data, social media data, sensor data, movement data,temperature data, and/or other types of data described or contemplatedherein.

In some embodiments, the client devices 104 and 106 may include or takethe form of a smartphone system, a personal computer (PC) such as alaptop device, a tablet computer device, a wearable computer device, ahead-mountable display (HMD) device, a smart watch device, and/or othertypes of computing devices configured to transfer data. The clientdevices 104 and 106 may include various components, including, forexample, input/output (I/O) interfaces 130 and 140, communicationinterfaces 132 and 142, hardware processors 134 and 144, andnon-transitory data storages 136 and 146, respectively, all of which maybe communicatively linked with each other via a system bus, network, orother connection mechanisms 138 and 148, respectively.

The I/O interfaces 130 and 140 may be configured to receive inputs fromand provide outputs to respective users of the client devices 104 and106. For example, the I/O interface 130 may include a display thatprovides a graphical user interface (GUI) configured to receive an inputfrom a user to create, configure, and/or modify one or more dataexchange schemas. Thus, the I/O interfaces 130 and 140 may includedisplays configured to receive inputs and/or other input hardware withtangible surfaces, such as touchscreens with touch sensitive sensorsand/or proximity sensors. The I/O interfaces 130 and 140 may alsoinclude a microphone configured to receive voice commands, a computermouse, a keyboard, and/or other hardware to facilitate input mechanisms.In addition, I/O interfaces 130 and 140 may include output hardware suchas one or more sound speakers, other audio output mechanisms, hapticfeedback systems, and/or other hardware components.

In some embodiments, communication interfaces 132 and 142 may include ortake a variety of forms. For example, communication interfaces 132 and142 may be configured to allow client devices 104 and 106, respectively,to communicate with one or more devices according to a number ofprotocols described and/or contemplated herein. For instance,communication interfaces 132 and 142 may be configured to allow clientdevices 104 and 106, respectively, to communicate with the server 102via the one or more communication networks 108. The hardware processors134 and 144 may include one or more multi-purpose processors,microprocessors, special purpose processors, digital signal processors(DSP), application specific integrated circuits (ASIC), programmablesystem-on-chips (SOC), field-programmable gate arrays (FPGA), and/orother types of processing components.

The non-transitory data storages 136 and 146 may include one or morevolatile or non-volatile data storages, removable or non-removable datastorages, and/or a combination of such data storages that may beintegrated in whole or in part with the hardware processors 134 and 144,respectively. Further, data storages 136 and 146 may includenon-transitory memories that store instructions and/or instructionssets. Yet further, the processors 134 and 144 may be coupled to the datastorages 136 and 146, respectively, and configured to read theinstructions from the non-transitory memories to cause the clientdevices 104 and 106 to perform operations, respectively, such as thosedescribed in this disclosure, illustrated by the accompanying figures,and/or otherwise contemplated herein.

FIG. 1B is a block diagram of another exemplary system, according to anembodiment. As shown, the system 150 may be configured to transfer data,such as data and/or data packets 122 and/or 124, as described above inrelation to system 100 in FIG. 1A. For example, the system 150 includesthe server 102, shown as a data exchange schema server 102. Further, thesystem 150 includes the client devices 104 and 106, and also the one ormore networks 108. As illustrated, the data infrastructure 150 mayinclude one or more communication servers 152, one or more applicationservers 160, and/or one or more database servers 166.

In some embodiments, the one or more communication servers 152 mayinclude a web server 154, an application programming interface (API)server 156, and/or a message server 158. The web server 154 may beconfigured to communicate with the client devices 104 and/or 106 overthe one or more networks 108. The web server 154 may host numerous webbrowsers, web sites, web-based applications, software applications,virtual machines, and/or other possibilities. The API server 156 may beconfigured to communicate with various applications of the clientdevices 104 and/or 106, including service provider applicationsconfigured to communicate with API-based communications and/or protocolsover the one or more networks 108. The message server 158 may beconfigured to communicate with the client devices 104 and/or 106 overthe one or more networks 108 with various transmissions, communicationmediums, and/or related applications such as e-mail, local area network(LAN) messaging, and/or short message service (SMS), among various otherpossibilities. Notably, any two or more of the servers 154, 156, and/or158 may be combined and the combined server may be configured to performa one or more operations of the servers 154, 156, and/or 158 asdescribed and/or contemplated herein.

In some embodiments, the one or more application servers 160 may includethe data exchange schema server 102, the user controls server 162,and/or the user account server 164. The data exchange schema server 102may maintain, manage, and/or support numerous data exchange schemas forone or more users as described herein. The user controls server 162 maymaintain, manage, and/or support various user controls, configurations,and/or settings associated with the data exchange schemas for the one ormore users. The user account server 164 may maintain, manage, and/orsupport numerous user accounts for the one or more users, such as emailaccounts, networking accounts, and/or payment provider accounts, amongother types of accounts described and/or contemplated herein.

In some embodiments, the one or more database servers 166 may includethe database server 170, the data exchange schema database 168, and/orthe user account database 172. The database server 170 may communicatewith the data exchange schema server 102 to facilitate the storage ofdata, data types, and/or data entries of the data exchange schemas inthe data exchange schema database 168. The database server 170 may alsocommunicate with the user account server 164 to facilitate the storageof user account data in the user account database 172. In someembodiments, the data stored with the schema database 168 may correspondto the data stored with the user account database 172. As such, thedatabase server 170 may include one or more search indexes with varyingcomplexities to minimize replicated data entries stored in the schemadatabase 168 and the account database 172.

In practice, for example, a user operating the client device 104 maysend a request over the one or more networks 108 to create one or moredata exchange schemas. Referring back to FIG. 1A, for example, therequest may be embedded with the data/data packet 122. As such, therequest may be transmitted to the one or more communications servers 152to request a connection with the data exchange schema server 102. Forexample, the web server 154, possibly referred to as a domain nameserver (DNS) in this scenario, may search and identify one or moreinternet protocol (IP) addresses of the data exchange schema server 102,possibly taking the form of 192.168.102. As such, a connection with theclient device 104 and the data exchange schema server 102 may beestablished to create the one or more data exchange schemas. Notably,the client device 104 may establish such connections with the schemaserver 102 with or without user inputs, possibly to generate, build,and/or modify the data exchange schemas in real-time, possiblyunbeknownst to the user of the client device 104.

In some embodiments, the system 150 may be referred to as a dataexchange system 150. In particular, the data exchange system 150 mayinclude the non-transitory memory 114 for storing instructions. The dataexchange system 150 may also include the one or more of hardwareprocessors 112 coupled to the non-transitory memory 114 and configuredto read the instructions to cause the system 150 to perform operations.The system 150 may create one or more data exchange schemas for a userwith or without the user's inputs, where each data exchange schemacompiles one or more types of data associated with the user. The system150 may determine a location of the client device 104, possibly based onthe connection between the client device 104 and the data exchangeschema server 102 described above.

In some instances, the location, such as the doctor's office describedabove, may be associated with one or more entities (e.g., the doctor'sstaff, medical insurance companies, and/or drug stores in the abovescenarios). In response to determining the location of the clientdevice, the system 150 may determine a given data exchange schema fromthe one or more data exchange schemas based on the one or more entities.For example, the data exchange schema identified may be configured forthe scenario where the user visits the doctor's office. The system 150may determine an access of the one or more entities to a portion of datafrom at least one data exchange schema. For example, the system 150 mayprovide the doctor's office with limited access to the user's medicalhistory such that the information cannot be transferred to otherentities without the user's permission. The system 150 may transmit anotification to the client device that indicates the access of the oneor more entities to the portion of data.

It can be appreciated that the data exchange schema server 102 and theclient devices 104 and/or 106 may be deployed in various other ways. Forexample, the operations performed by the server 102 and/or the clientdevices 104 and 106 may be performed by a greater or a fewer number ofdevices. Further, the operations performed by two or more devices, suchas the servers 102, 162, and/or 164, may be combined and performed by asingle device, such as the server 102. Yet further, the operationsperformed by a single device, such as the server 102, may be separatedor distributed among the server 102, the client devices 104 and/or 106,the user controls server 162, and/or the user account server 164, amongother possible devices. In addition, the client devices 104 and/or 106may be operated and/or maintained by different users such that eachclient device 104 and/or 106 may be associated with one or moreaccounts.

Notably, one or more user accounts maintained by the user account server164 may be displayed on the client device 104, possibly through the I/Ointerface 130 described above. As such, a user account may be displayedon a smartphone system to provide the user with access to the account.In some instances, the user may access the one or more accounts to viewthe number of data exchange schemas shared with one or more entities.Yet further, the user may access the data exchange schemas to view theone or more accounts.

In some embodiments, an account, possibly referred to a user account,may take a number of different forms. For example, an account may be ane-mail account, a networking account, a professional and/or a socialnetworking account, a smartphone account, a music or music playlistaccounts, and/or a video streaming account, among other possibleaccounts. Further, an account may include a compilation of dataassociated with a given user. For example, an account for a particularuser may include data related to the user and/or the user's interests.Some examples of accounts may include accounts with service providersdescribed above, e-commerce accounts, and/or accounts with funds,balances, fund transfers, transactions, and/or check-outs, among otherpossibilities.

In some embodiments, a user may have a single user account with a givenservice provider that may represent the user for multiple other serviceproviders, applications, and/or services, among other possibilities. Forexample, the single user account may represent the user for e-mailaccounts, networking or social networking accounts, smartphone accounts,as well as websites, applications, and/or other services. As such, auser could opt to use the single user account as a multi-purpose accountfor performing various operations, including managing one or more dataexchange schemas for the user.

In some embodiments, a user account may be created for one or moreusers. For example, an account may be a family account created formultiple family members, where each member may have access to theaccount. In some instances, the account may be a corporate account,where employees, staff, worker personnel, and/or contractors, amongother individuals may have access to the corporate account. Yet further,it should be noted that a user, as described herein, may be a number ofindividuals or possibly a robot, a robotic system, a computing device, acomputing system, and/or another thin′ of technology capable oftransferring data corresponding to the account. The user may be requiredto provide a login, a password, a code, an encryption key,authentication data, and/or other types of data to access the account.

FIG. 2A illustrates exemplary system 200 configured to support a set oftrays 204 and 206, according to an embodiment. The system 200 may, forexample, include or take the form of the server 102 described above inrelation to FIGS. 1A and 1B. In particular, the system 200 may also bereferred to as the server 200 and/or the server system 200. As such, thesystem 200 may manage numerous data exchange schemas for the users ofclient devices, such as the client devices 104 and/or 106. The system200 may further support, operate, run, and/or manage the data exchangeschemas, possibly in addition to various applications, websites, and/orservices.

As shown, the system 200 may include a chassis 202 that may supporttrays 204 and 206, possibly also referred to as servers or server trays204 and/or 206. Notably, the chassis 202 may support multiple otherservers and/or trays as well. The chassis 202 may include slots 208 and210, among other possible slots, configured to hold or support trays 204and 206, respectively. For example, the tray 204 may be inserted intothe slot 208 and the tray 206 may be inserted into the slot 210. Yet,the slots 208 and 210 may be configured to hold the trays 204 and 206interchangeably such that the slot 208 may be configured to hold thetray 206 and the slot 210 may be configured to hold the tray 204.

Further, the chassis 202 may be connected to a power supply 212 viaconnections 214 and 216 to provide power to the slots 208 and 210,respectively. The chassis 202 may also be connected to the communicationnetwork 218 via connections 220 and 222 to provide network connectivityto the slots 208 and 210, respectively. As such, trays 204 and 206 maybe inserted into slots 208 and 210, respectively, and power supply 212may supply power to trays 204 and 206 via connections 214 and 216,respectively. Further, trays 204 and 206 may be inserted into the slots210 and 208, respectively, and power supply 212 may supply power totrays 204 and 206 via connections 216 and 214, respectively.

Yet further, trays 204 and 206 may be inserted into slots 208 and 210,respectively, and communication network 218 may provide networkconnectivity to trays 204 and 206 via connections 220 and 222,respectively. In addition, trays 204 and 206 may be inserted into slots210 and 208, respectively, and communication network 218 may providenetwork connectivity to trays 204 and 206 via connections 222 and 220,respectively. The communication network 218 may, for example, take theform of the one or more communication networks 108, possibly includingone or more of a data network and a cellular network. In someembodiments, the communication network 218 may provide a network port, ahub, a switch, or a router that may be connected to an Ethernet link, anoptical communication link, a telephone link, among other possibilities.

In practice, the tray 204 may be inserted into the slot 208 and the tray206 may be inserted into the slot 210. During operation, the trays 204and 206 may be removed from the slots 208 and 210, respectively.Further, the tray 204 may be inserted into the slot 210 and the tray 206may be inserted into the slot 208, and the system 200 may continueoperating, possibly based on various data buffering mechanisms of thesystem 200. Thus, the capabilities of the trays 204 and 206 mayfacilitate uptime and the availability of the system 200 beyond that oftraditional or conventional servers that may be required to run withoutinterruptions. As such, the server trays 204 and/or 206 facilitatefault-tolerant capabilities of the server system 200 to further extendtimes of operation. In some instances, the server trays 204 and/or 206may include specialized hardware, such as hot-swappable hard drives,that may be replaced in the server trays 204 and/or 206 duringoperation. As such, the server trays 204 and/or 206 may preventinterruptions to further increase uptime.

FIG. 2B illustrates an exemplary tray 204 configured to support one ormore components, according to an embodiment. The tray 204, possibly alsoreferred to as the server tray 204, may take the form of the tray 204described in relation to FIG. 2A. Further, the tray 206 may also takethe form of the tray 204. As shown, the tray 204 may include a tray base230 that may include the bottom surface of the tray 204. The tray base230 may be configured to support multiple components such as the harddrives described above and a main computing board connecting one or morecomponents 232-240. The tray 204 may include a connection 226 that maylink to the connections 214 or 216 to supply power to the tray 204. Thetray 204 may also include a connection 228 that may link to theconnections 220 or 222 to provide network connectivity to the tray 204.The connections 226 and 228 may be positioned on the tray 204 such thatupon inserting the tray 204 into the slot 208, the connections 226 and228 couple directly with the connections 214 and 220, respectively.Further, upon inserting the tray 204 into the slot 210, the connections226 and 228 may couple directly with connections 216 and 222,respectively.

In some embodiments, the tray 204 may include a hardware processorcomponent 232, a non-transitory memory component 234, a non-transitorydata storage component 236, a communication interface component 238,that may, for example, take the form of the processor 112, the memory114, the data storage 116, and the communication interface 118,respectively. Further, the tray 204 may include the data enginecomponent 240 that may manage data exchange schemas for numerous users.As such, the connections 226 and 228 may be configured to provide powerand network connectivity, respectively, to each of the components232-240. In some embodiments, one or more of the components 232-240 mayperform operations described herein, illustrated by the accompanyingfigures, and/or otherwise contemplated.

As shown, the hardware processor component 232 may take the form of amulti-purpose processor, a microprocessor, a special purpose processor,a digital signal processor (DSP). Yet further, the processor component232 may take the form of an application specific integrated circuit(ASIC), a programmable system on chip (PSOC), field-programmable gatearray (FPGA), and/or other types of processing components. Inparticular, the processor component 232 may create, modify, and/or builddata exchange schemas for numerous users. For example, the processorcomponent 232 may be configured with a Unix-based operating system.Further, the processor component 232 may support the scalability ofnumerous data exchange schemas developed with various other servers,such as those described above in relation to the data infrastructure150. In particular, the processor component 232 may be configured tofacilitate the scalability with multiple such servers of various formsthat may, for example, include server trays, blades, and/or cartridgessimilar to the server trays 204 and/or 206. In some instances, theprocessor component 232 may be configured with scalable processarchitectures, including, reduced instruction set architectures. In someinstances, the processor component 232 may be backwards compatible withvarious legacy systems such that the processor component 232 mayreceive, read, and/or execute instruction sets with legacy data formatsand/or structures. As such, the processor component 232 generally hascapabilities beyond that of general-purpose processors.

The database engine component 240 may include one or more securedatabases to support, manage, and/or maintain data exchange schemas fornumerous users. In particular, the data base engine component 240 mayorganize and/or format the data exchange schemas for optimizing searchesand/or retrieving data. In various circumstances, the database enginecomponent 240 may perform searches based on numerous queries, searchmultiple databases in parallel, and produce search resultssimultaneously and/or consecutively. Thus, the database engine component240 may relieve various bottlenecks encountered with conventionalservers managing numerous accounts.

Any two or more of the components 232-240 described above may becombined. For example, two or more of the hardware processor component232, the non-transitory memory component 234, the non-transitory datastorage component 236, the communication component and/or interface 238,and/or the data engine component 240 may be combined. Further, thecombined component may take the form of one or more processors, DSPs,SOCs, FPGAs, and/or ASICs, among other types of processing devicesand/or components described herein. For example, the combined componentmay take the foal′ an SOC that integrates various other components in asingle chip with digital, analog, and/or mixed-signal functions, allincorporated within the same substrate. As such, the SOC may beconfigured to carry out various operations of the components 232-240.

The components 232-240 described above may provide advantages overconventional or general-purpose components. For example, the components232-240 may enable the system 200 to transfer data over the one or morenetworks 218 to numerous other client devices, such as the clientdevices 104 and/or 106. In particular, the components 232-240 may enablethe system 200 to build data exchange schemas for numerous users locallyfrom a single server tray 204. In some instances, configuring a separateand/or dedicated hardware processor component 232 to manage the dataexchange schemas may optimize operations beyond the capabilities ofconventional servers and/or general-purpose processors. As such, theaverage wait time for the client device 104 to display data from thedata exchange schemas may be minimized accordingly.

It can be appreciated that the system 200, the chassis 202, the trays204 and 206, the slots 208 and 210, the power supply 212, thecommunication network 218, and the components 232-240 may be deployed inother ways. The operations performed by components 232-240 may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of components or devices. Further, one ormore components or devices may be operated and/or maintained by the sameor different entities.

FIG. 3A illustrates a data exchange system 300, according to anembodiment. As shown, the system 300 manages, maintains, and/or supportsone or more data exchange schemas 302 and/or 304, among other possibledata exchange schemas contemplated. In particular, the system 300 maymanage one or more databases 306 and/or 308 in the data exchange schema302, among other possible databases as shown with the ellipses below thedatabase 308. Further, the system 300 may manage one or more databases310 and/or 312 in the data exchange schema 304, among other possibledatabases as shown with the ellipses below the database 312. Notably,the data exchange system 300 may include one or more of the systemsdescribed above (e.g., 100, 150, and/or 200) to manage, maintain, and/orsupport the one or more data exchange schemas 302 and/or 304.

As shown, the database 306 of the data exchange schema 302 may includeone or more types of data. For example, the database 306 may includebirthday data 316. Notably, various aspects of the birthday data 316 maybe derived, possibly based on one or more data exchange schemas, such asthe data exchange schemas 302 and/or 304. For instance, the day, month,and/or year of the user's birthday, the age of the user, and/or thebirth place of the user may be derived from the data exchange schemas302 and/or 304. Further, the birthplace of the user may be derived basedon aggregating other forms data from the data exchange schemas 302and/or 304 to identify a city, state, and/or the country of the user'sbirthplace.

Further, the database 306 may be used to derive and/or aggregate variousother types of data that may identify the user. For example, thedatabase 306 may include the user's name (e.g., first, middle, andlast), the gender of the user, social security number, and/or driver'slicense number, among other types of data that may identify the user.Yet further, the database 306 may also be used to derive the user'semail address, home address, shipping address, billing address, workaddress, and/or telephone number, among other types of data that may beused to contact the user. Notably, the user's address in the database306 may be derived from one or more other data exchange schemas, such asthe data exchange schemas 302 and/or 304. For example, the city, state,country, and/or region of the country associated with the user's addressmay be derived from aggregating other forms of data from the dataexchange schemas 302 and/or 304, as described herein.

Further, the database 306 of the data exchange schema 302 may includeaccount data 318. The account data 318 may include various types of datarelated to a user's account, such as an account with a service provider,among other types of accounts described above (e.g., e-mail accounts,communications accounts, and/or networking accounts). In some instances,the account data 318 may indicate a balance, bank account data, a creditcard number, a debit card number, and/or a transaction history, amongother types of data associated with transferring fund amounts from theuser's account. Yet, the database 306 may be used to derive variousother types of data as shown with the ellipses below the account data318.

Yet further, the database 308 of the data exchange schema 302 mayinclude one or more other types of data. For example, the database 308may include a height 320 of the user, possibly indicating the height ofthe user over a number of years. For example, a number of changes to theheight of the user over the years may be derived from the database 308.Further, the database 308 may be used to derive various other types ofdata related to the user's traits, features, and/or characteristics. Forexample, the database 308 may be used to derive the user's waistmeasurements, pant length, shoe size, weight, head size, hair color,body type, and/or facial structure, among other types of data related tothe user's physical attributes.

In addition, the database 308 of the data exchange schema 302 mayinclude medical data 322. The medical data 322 may include various typesof data related to the user's medical history as described above. Forexample, the medical data 322 may be used to derive the user'sallergies, vitals measurements, blood pressure, blood type, medicalinsurance information, medical history, medications or immunizationstaken, prescriptions provided to the user, among other types of datarelated to the user's medical history.

Referring to the data exchange schema 304, the database 310 may includeone or more types of data, possibly related to the user's location. Forexample, referring back to FIGS. 1A and 1B, various forms of locationdata may be retrieved based on the connection established with theclient device 104 and/or the data exchange schema server 102. Forexample, based on one or more data exchanges for establishing theconnection, the data exchange schema server 102 may retrieve Wi-Fibeaconing data, Enhanced Observed Time Difference (EOTD) data, globalpositioning System (GPS) data, Assisted GPS (A-GPS) data, DifferentialGPS (DGPS) data, Time Difference of Arrival (TDOA) data, Angle ofArrival (AOA) data, triangulation data, local transceiver pilot signaldata, among other forms of location data described above.

Further, the database 310 of the data exchange schema 304 may includeone or more types of data, possibly related to the user's device and/ordevices. For example, the database 310 may include the IP address data326, possibly indicating the IP address of the user's device, such asthe client device 104 described above. For example, the IP address data326 of the client device may be a numerical representation assigned tothe client device based on a connection to the one or more networks,such as the one or more networks 108 described above. As such, the IPaddress of the client device may be shared with one or more entities toestablish other connections and/or communications. Notably, the accessto the IP address data 326 may be hidden and/or shared in a controlledmanner with the given accesses provided to the data exchange schema 304.

Yet further, the database 312 of the data exchange schema 304 mayinclude one or more types of data, possibly related to the user'sinteractions with the one or more devices. For example, the database 312may include browse data 328 that indicates the sites, websites,applications, browsers, searches, search strings, and/or searchhistories of the user, among other possibilities related to the userbrowsing with one or more devices. Further, the database 312 may includeclick data 330 that indicates the user selections, possibly associatedwith the browsing described above. In particular, the click data 330 mayindicate various links that the user selects and/or interacts with insome manner, among other possibilities that may indicate the user'sinterests.

Notably, the data exchange schemas 302 and/or 304 may include one ormore types of data. Further, the schemas 302 and/or 304 may includedifferent levels of specificity. For example, the schemas 302 and/or 304may include broad types or levels such as music preference or genre.Further, the schemas 302 and/or 304 may also include types or levelswith more specificity such as particular artists, albums, and/or songs.Each of these various types or levels of data may be accessible by oneor more entities based on how the data may be used.

As shown, the data exchange system 300 may provide one or more accesses332 and/or 334 to the one or more entities 314. For example, considerthe scenario where the user visit's the doctor's office. Based on theuser entering the doctor's office, the user's device and the doctor'soffice may communicate and exchange data, possibly based on a WIFIconnections. The system 300 may identify the data exchange schema 302associated with the user visiting the doctor's office. In particular,the system 300 may identify the data exchange schema 302 from a numberof different schemas associated with the user, including the dataexchange schema 304. As such, the system 300 may search and identify thebirthday data 316 and/or the account data 318 related to the uservisiting the doctor's office. In some instances, the system 300 mayderive the user's birthday, the user's age, and/or the user's birthplacebased on the various forms of data in the data exchange schemas 302and/or 304, as described above. Further, the system 300 may provide suchdata to the user's device, possibly allowing the user to add furtherdata to the birthday data 316 and/or the account data 318. For example,the use may add the user's symptoms in the previous hours or days,possibly being the basis for the user visiting the doctor's office. Assuch, the birthday data 316, the account data 318, and/or a descriptionof the user's symptoms may be provided to doctor's staff, described inthis scenario as the one or more entities 314.

In some embodiments, the data exchange system 300 includes anon-transitory memory storing instructions and one or more hardwareprocessors. For example, referring back to FIGS. 1A-2B, the dataexchange system 300 includes the non-transitory memory 114 and/or 234that stores the instructions. The one or more one or more hardwareprocessors 112 and/or 232 is coupled to the non-transitory memory 114and/or 234 to read the instructions. As such, the data exchange system300 performs operations. The operations include determining one or moredata exchange schemas 302 and/or 304 for a user, where each dataexchange schema 302 and/or 304 compiles one or more types of dataassociated with the user. The operations also include determining alocation 324 of a client device of the user, such as the client device104 described above, where the location 324 is associated with one ormore entities 314. In response to determining the location 324 of theclient device, the operations may include determining the data exchangeschema 302 from the one or more data exchange schemas 302 and/or 304based on the one or more entities 314. The operations may includedetermining accesses 332 and/or 334 of the one or more entities 314 toat least a portion of data 316 and/or 318 from the data exchange schema302. The operations may include transmitting a notification to theclient device, e.g., the client device 104, that indicates the accesses332 and/or 334 of the one or more entities 314 to the portion of data316 and/or 318, respectively, from the data exchange schema 302.

In some embodiments, the data exchange system 300 may provide theaccesses 332 and/or 334 to the one or more entities 314 based on varioustimes recognized. For example, the data exchange system 300 may retrievethe user's schedule from the client device 104 described above to beoperated by the user. For example, referring back to FIG. 1B, the dataexchange schema server 102 may request and receive the user's schedulebased on the connection established with the client device 104 asdescribed above. As such, the data exchange system 300 may performoperations that include determining one or more times associated with auser schedule accessible with the client device 104 of the user. Assuch, the accesses 332 and/or 334 of the one or more entities 314 to theportion of the data 316 and/or 318 may be determined based on the one ormore times determined.

It should be noted that the one or more data exchange schemas 302 and/or304 may also be determined by the data exchange system 300 based oninputs from the user. For example, referring back to FIG. 1A, the system300 may recognize inputs received from a graphical user interface, e.g.,the I/O interface 130, of the client device 104 that indicates the oneor more types of data. As noted, the one or more types of data indicatedmay include the birthday data 316 and/or the account data 318. Inparticular, the system 300 may recognize such inputs based on dataretrieved from the client device 104 during a connection protocol withthe data exchange schema server 102. As such, the one or more dataexchange schemas 302 and/or 304 may be determined from the one or moreuser inputs.

FIG. 3B illustrates a data exchange system 300 with another entity,according to an embodiment. As shown, the data exchange system 300includes the data exchange schemas 302 and/or 304 from FIG. 3A. As such,the data exchange schema 302 includes the database 306, furtherincluding the birthday data 316, the account data 318, and/or othertypes of data. As also shown, the one or more entities 314 have accesses332 and/or 334 to the birthday data 316 and/or the account data 318,respectively. Yet further, the data exchange schema 302 includes thedatabase 308, further including the height data 320, the medical data322, and/or other types of data. In addition, the data exchange schema304 includes the database 310, further including the location data 324,the IP address data 326, and/or other types of data. Further, the dataexchange schema 304 includes the database 312, further including thebrowse data 328, the click data 330, and/or other types of data.

As also shown, the one or more entities 314 may have accesses 338 and/or340 to the height data 320 and/or medical data 322, respectively.Considering the scenario regarding the doctor's office above, the system300 may request the user's permission before providing the one or moreentities 314 with the accesses 338 and/or 340 to the height data 320and/or medical data 322, respectively. One possible difference in thisparticular scenario is that the one or more entities 314 may be giventhe accesses 332 and/or 334 without the system 300 requesting the user'spermission. As noted, the accesses 332 and/or 334 may be provided to thedoctor's office based on the location 324 of the client device of theuser.

Yet further, also shown in FIG. 3B is the one or more entities 336.Consider, for example, that the one or more entities 336 includes astore that the user that the user visits often. In particular, the oneor more entities 336 may represent a merchant of the store and/or agroup of merchants associated with the store. As such, the system 300may also determine the one or more data exchange schemas 302 and/or 304based on the user's interactions with the one or more entities 336. Asshown, for example, the one or more entities 336 may have accesses 332and/or 334 to the user's birthday data 316 and/or the account data 318,respectively.

Yet, it should be noted that the accesses 332 and/or 334 for the one ormore entities 336 may be the same or different than those for the one ormore entities 314. For example, the one or more entities 314 may havethe access 334 to the account data 318 for purposes of the doctor'soffice, possibly including charges associated with the doctor's officesuch as copays, prescription costs, and/or other related charges. Yet,the one or more entities 336 may have the access 334 to the account data318 for the user's balance with the store, possibly for deducting fromthe balance when the user wishes to purchase items from the store. Insome instances, the access 334 may be based on the specific purposesand/or uses by the entities 314 and/or 336, and may further be definedby a set of rights to the account data 318.

As such, the access 334 of the one or more entities 314 to the accountdata 318 may be limited in one or more different implementations. Forexample, the access 334 to the entities 314 and/or 336 may restrict theentities 314 and/or 336 from transferring the account data 318 to otherentities. In some instances, the accesses 334 to the account data 318may be controlled, from any such remote servers and/or computers.Further, the access 334 may prevent the entities 314 and/or 336 fromsaving and/or storing the account data 318 to unsecured servers and/orcomputers, possibly based on various data configurations of the accountdata 318. For example, the account data 318 may be protected with anumber of cryptographic protocols and/or encryption layers that securethe account data 318 from unauthorized entities as described above. Assuch, the system 300 may control varying instances where the accountdata 318 is unencrypted such that the entities 314 and/or 336 may havethe access 334 to the account data 318 for one or more defined purposes.

In addition, FIG. 3B shows the accesses 342 and/or 344 of the one ormore entities 336 to the location data 324 and/or the browse data 328,respectively. For example, the user may have downloaded an applicationof the store, possibly referred to as a mobile app, that may beassociated with the one or more entities 336. As such, the app may havelocation enabling services and user browse history and/or trackingservices to have the accesses 342 and/or 344 to the location data 324and/or the browse data 328, respectively. Notably, under some practices,the one or more entities 336 may have the accesses 342 and/or 344 to thelocation data 324 and/or the browse data 328, respectively, possiblyunbeknownst to the user. Yet, as further described herein, the system300 may enable the user to be aware of the accesses 342 and/or 344,among various other accesses, such as the accesses 332, 334, 338, and/or340, and further control such accesses accordingly.

In some embodiments, the one or more data exchange schemas 302 and/or304 may be determined based on a communication of the user's clientdevice. For example, the system 300 may determine a data transfer fromthe client device with one or more types of data. As noted with thescenario above involving the mobile app, the system 300 may determinevarious data transfers associated with the app. Referring back to FIG.1B, for example, the data exchange schema server 102 may communicatewith the API server 156 to determine the data transfers associated withthe app installed on the client device 104. As such, the system 300 maydetermine data transfers of one or more types of data based acommunication of the client device with a remote device, such as the APIserver 156. In such instances, the one or more data exchange schemas 302and/or 304 may be determined based on the data transfer of the one ormore types of data.

FIG. 3C illustrates a data exchange system 300 with yet another entity,according to an embodiment. As shown, the data exchange system 300includes the data exchange schemas 302 and/or 304 from FIGS. 3A and 3B.Further, the data exchange schema 302 includes the database 306, furtherincluding the birthday data 316, the account data 318, and/or othertypes of data. As also shown, the one or more entities 314 and/or 336may have accesses 332 and/or 334 to the birthday data 316 and/or theaccount data 318, respectively. Yet further, the data exchange schema302 includes the database 308, further including the height data 320,the medical data 322, and/or other types of data. As illustrated, theone or more entities 314 may have accesses 338 and/or 340 to the heightdata 320 and/or the medical data 322, respectively.

In addition, the data exchange schema 304 includes the database 310,further including the location data 324, the IP address data 326, and/orother types of data. Further, the data exchange schema 304 includes thedatabase 312, further including the browse data 328, the click data 330,and/or other types of data. As shown, the one or more entities 336 mayhave accesses 342 and/or 344 to the location data 324 and/or the browsedata 328, respectively, as described above.

Yet further, also shown in FIG. 3C is the one or more entities 346.Consider, for example, that the one or more entities 346 includes anonline store, possibly an online store that the user has visitedpreviously. For example, the one or more entities 346 may represent anonline merchant and/or a group of online merchants. As such, the system300 may also determine the one or more data exchange schemas 302 and/or304 based on the user's interactions with the one or more entities 346,and/or various online websites of the one or more entities 346. Asshown, for example, the one or more entities 346 may have accesses 344,348, and/or 350 to the browse data 328, the IP address data 326, and/orthe click data 330, respectively.

In addition, as also shown in FIG. 3C, a number of rules 352, 354,and/or 356 are provided. In some instances, the accesses 332, 334, 338,and/or 340 may be determined based on the rule 352. For example, therule 352 may allow the one or more entities 314 to transfer the data316, 318, 320, and/or 322 to other entities, possibly with permission(s)from the user. Yet, the rule 352 may not allow the one or more entities336 to transfer data 316, 318, 320, and/or 322 to other entities,possibly with or without permissions from the user. Notably, the rules352, 354, and/or 356 may be created by the system 300 and/or based oninputs from the user.

In some instances, the accesses 342 and/or 348 may be determined basedon the rule 354. For example, the rule 354 may allow the one or moreentities 336 to transfer the data 324 to other entities, possibly withpermission from the user. Yet, the rule 354 may not allow the one ormore entities 346 to transfer the IP address data 326 to other entities,possibly with or without permissions from the user. In some instances,the system 300 may identify an external access 358 from the entity 346,where other entities may retrieve the IP address data 326. As such, therule 354 may not allow the one or more entities 346 to transfer the IPaddress data 326 to other entities.

As also shown, the access 344 may be determined based on the rule 356.Further, the access 350 may be determined without the rule 356. As such,the one or more entities 346 may have accesses 344 and/or 350 that aredetermined without any rules, possibly allowing the one or more entities346 to transfer the data 328 and/or 330 based on the external access 358to one or more other entities. Notably, the access 344 of the entity 346to the browse data 328 may not be subject to the rule 356, whereas theaccess 344 of the entity 336 to the browse data 328 may be subject tothe rule 356. As such, the access 344 for the one or more entities 336may be different than the access 344 for the one or more entities 346.As noted, the one or more entities 346 may transfer the browse data 328to one or more other entities based on the external access 358.

In some embodiments, the data exchange system 300 may perform furtheroperations to control the accesses 332, 334, 338, 340, 342, 344, 348,and/or 350 based on user inputs and/or controls. For example, usercontrols may be received to determine the accesses 332, 334, 338, and/or340 with the rule 352. Further, the user controls may be received todetermine the accesses 342 and/or 348 with the rule 354. Yet further,the user controls may be received to determine the accesses 344 and/or350 with the rule 356. As such, the operations of the data exchangesystem 300 may be performed where at least one of the data exchangeschemas 302 and/or 304 is associated with one or more access rules 352,354, and/or 356 determined by the user. As noted, for example, theaccess 334 of the one or more entities 314 and/or 336 to the portion ofdata 318 may be determined based at least on a particular access rule352 from the one or more access rules 352, 354, and/or 356 determined.Notably, the user controls may be received to provide the accesses 332,334, 338, 340, 342, 344, 348, and/or 350 for a given time duration andthe accesses may then be removed after the termination of the timeduration. Further, the accesses 332, 334, 338, 340, 342, 344, 348,and/or 350 may be recorded in a number of logs such that the user mayview the accesses accordingly.

In some embodiments, the data exchange system 300 may perform furtheroperations to inform the user whether one or more types of data 316-330is shared with the one or more entities 314, 336 and/or 346, among otherpossible entities. For example, referring back to FIGS. 1A-3B, thesystem 300 may transmit notifications over the one or more networks 108to the client device 104 of the user such that the user can view thenotifications on the I/O interface 130, possibly including a graphicaluser interface with such notifications. In particular, the system 300may perform operations including determining the one or more entities346 permitted to share the portion of data 328 and/or 330 based on aparticular access rule 356 associated with the portion of data 328and/or 330. The system 300 may perform further operations includingdetermining one or more second or other entities that may receive theportion of the data 328 and/or 330 from the one or more entities 346,possibly based on the access 358. The system 300 may transmitnotifications to the client device to further indicate the one or moresecond or other entities that received the portion of the data 328and/or 330. Notably, the system 300 may tag the data 328 and/or 330 toidentify the one or more second or other entities that received orpossess the data 328 and/or 330.

In some embodiments, the data exchange system 300 may perform furtheroperations to transmit suggestions to manage, control, and/or limit theaccesses 332, 334, 338, 340, 342, 344, 348, and/or 350 to the dataexchange schemas 302 and/or 304. For example, the system 300 maytransmit suggestions to the user based on how the data 316, 318, 320,322, 324, 326, 328, and/or 330 may be used by the one or more entities314, 336, and/or 346, among other possible entities. In particular, thesystem 300 may transmit suggestions to the user based on the entity 346sending advertisements to the user based on the browse data 328 and/orthe click data 330. Yet further, the system 300 may transmit suchsuggestions based on the external access 358 that one or more second orother entities may have to the browse data 328 and/or the click data330, possibly resulting in additional advertisements sent to the user.Notably, in some instances, the system 300 may also determine thesuggestions based on how merchants of the entities 314, 336, and/or 346would like to receive data 316-330.

In one scenario, the accesses 344 and/or 350 of the one or more entities346 to the portion of data 328 and/or 330 further enables one or moresecond or other entities to access the portion of data 328 and/or 330based on a particular access rule 356 associated with the portion of thedata 328 and/or the lack of an access rule associated with the portionof data 330. As such, the system 300 may perform operations includingdetermining a suggested change to the particular access rule 356 and/orcreating an access rule for the access 350 based on the one or moresecond entities with access to the portion of data 328 and/or 330. Thenotification transmitted to the client device as described above mayfurther indicate the suggested change to the particular access rule 356and/or the creation of the access rule for the access 350.

It should be noted that the data 316, 318, 320, 322, 324, 326, 328,and/or 330 in the one or more schemas 302 and/or 304 may changedynamically. Referring back to FIGS. 1B-3C, for example, the dataexchange schema server 102 may change the data in such schemas based onvarious communications with other servers, including the user accountserver 164 and/or the communication servers 152 further including theweb server 154, the API server 156, and/or the message server 158. Inparticular, the one or more schemas 302 and/or 304 may changedynamically based on the variability of the account data 318 deter linedby the system 300. For example, the user's medical history can changeover time. Further, various changes may incur to the user's address,shipping address, billing address, work address, and/or telephone, amongother characteristics involving the user may be determined from theuser's changes to the account data 318. In one or more scenarios, thedata exchange system 300 may perform operations including determining achange to the portion of data 316-330 accessible by the one or moreentities 314, 336, and/or 346. Further, the system 300 may performoperations including determining second accesses or updated accesses ofthe one or more entities 314, 336, and/or 346 to the changed portion ofdata 316-330, where the second or updated accesses of the one or moreentities 314, 336, and/or 346 may be based on a particular access ruleof the access rules 352, 354, and/or 356 associated with the portion ofdata 316-330.

FIG. 4A illustrates an exemplary system 400 with a client device 402,according to an embodiment. The system 400, possibly referred to asmartphone system 400, may include the aspects of the systems 100, 150,200, and/or 300 described in relation to FIGS. 1A-3C. For example, theclient device 402 may include one or more components of the clientdevice 104 described above in relation to the FIGS. 1-3C.

As shown, the smartphone system 400 may include a display/graphical userinterface 404. In particular, the graphical user interface 404 mayprovide the data exchange schemas 302, 304, and/or other schemasassociated with a user. As such, the user may view the entities 314,336, and/or 346 that have the accesses to the data 316, 318, 320, 322,324, 326, 328, and/or 330, among other types of data associated with thedata exchange schemas 302 and/or 304 described above in relation toFIGS. 3A-3C. Further, the user may view the various access rules 352,354, and/or 356 associated with the data exchange schemas 302 and/or304. As shown, the graphical user interface 404 may receive a touchinput 414 to select a given rule. As illustrated, the rule 352 may beselected and/or the user may be able to view details of the rule 352.Further, the scroll bar 412 may be used to view other entities that mayhave access to data from the data exchange schemas 302 and/or 304.

The smartphone system 400 may also include a speaker/microphone 406, aside button 408, and/or a control button 410, among other possiblehardware components. The smartphone system 400 may also include anon-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine, such as thesmartphone system 400, to perform operations. The smartphone system 400may also include one or more hardware processors that may take the formof the hardware processor 134 described above. The one or more hardwareprocessors may be coupled to the non-transitory machine-readable mediumand configured to read the instructions to cause the smartphone system400 to perform operations.

In some embodiments, the operations may include determining one or moredata exchange schemas 302 and/or 304 for a user, as described above inrelation to FIGS. 3A-3C. As noted, each data exchange schema 302 and/or304 includes one or more types of data 316-330 associated with the user.The operations may also include receiving a request from one or moreentities 314, 336, and/or 346 for at least a portion of data 316-330from at least one data exchange schema 302 and/or 304. For example, theportion of the data 316-330 requested may include a given type of datafrom the one or more types of data 316-330. In response to receiving therequest from the one or more entities 314, 336, and/or 346, an access332, 334, 338, 340, 342, 344, 348, and/or 350 for the one or moreentities 314, 336, and/or 346 may be determined. For example,considering the scenario above with one or more entities 346 includingan online store, the accesses 344 and/or 350 to the portion of data 328and/or 330, respectively, may be determined based at least on the typeof data in the portion of data 328 and/or 330. For example, the type ofdata may indicate user interactions with one or more browsers. Theoperations may include transmitting a notification to the client device402 of the user that indicates the access 344 and/or 350 of the one ormore entities 346 to the portion of data 328 and/or 330.

Notably, the user may access the data exchange schemas 302 and/or 304with the graphical user interface 404 of the client device 404. As such,the user may have access to various types of the data 316-330 from asingle view, possibly giving the user access to numerous types of dataassociated with the user. For example, the user may access the accountdata 318 to retrieve user names, passwords, PIN number, credit cardnumbers, frequent flyer mileage account numbers, and/or hotel rewardaccount numbers, possibly other information that may be forgotten. Insome instances, the control button 410 may include a fingerprint sensorto detect a fingerprint from one or more users to authenticate theuser's access to such information. For example, one or more of theuser's fingerprint inputs (e.g., thumb and index fingerprint inputs) maybe provided to the control button 410 to retrieve such information.

In some embodiments, the operations of smartphone system 400 may includegenerating one or more of the data exchange schemas 302 and/or 304,possibly based on user inputs to the graphical user interface (GUI) 404.For example, the one or more of the data exchange schemas 302 and/or 304may be generated by the data 316-330 shared based on inputs to the GUI404. For example, the operations may include determining a data transferwith a web browser of the client device 402 and a remote server based atleast on one or more touch inputs received from the GUI 404 of theclient device 402. As such, the one or more data exchange schemas 302and/or 304 may be determined based at least on the data transfer withthe web browser of the client device 402.

FIG. 4B also illustrates the exemplary system 400 with the client device402, according to an embodiment. As shown, the smartphone system 400 inFIG. 4B may take the form of the smartphone system 400 in FIG. 4A. Asnoted, the display/graphical user interface 404 may provide the dataexchange schemas 302, 304, and/or other schemas associated with a user.Yet further, the GUI 404 may provide the various access rules 352, 354,and/or 356 associated with the data exchange schemas 302 and/or 304. Inparticular, the GUI 404 may provide various permissions or permissionlevels of the entities 314 and/or 336 to transfer data based on the rule352. Further, the GUI 404 may provide various permission or permissionlevels of the entities 336 and/or 346 to transfer data based on the rule354. Yet further, the GUI 404 may provide various permissions of theentity 336 to transfer data based on the rule 356. As shown, the scrollbar 412 may be used to view other rules and permissions of entities thatmay have access to data from the data exchange schemas 302 and/or 304.

In some embodiments, the user may create or modify the access rules 352,354, and/or 356 with the GUI 404. For example, the user may modify theaccess rule 354 based on one or more user inputs to the GUI 404. Inparticular, the operations of the smartphone system 400 may includedetermining the one or more access rules 352, 354, and/or 356 associatedwith at least one of the data exchange schemas 302 and/or 304 based atleast on one or more touch inputs 414 received from the GUI of theclient device 402. For example, the one or more access rules 352, 354,and/or 356 may specify whether the entities 314, 336, and/or 346 maytransfer the data 316-330, with or without permissions, and/or underwhich circumstances or purposes. As such, for example, the accesses 344and/or 350 of the one or more entities 346 to the portion of data 328and/or 330 may be determined based on the one or more access rules 356determined.

FIG. 4C also illustrates the exemplary system 400 with the client device402, according to an embodiment. As shown, the smartphone system 400 inFIG. 4C may take the form of the smartphone system 400 in FIGS. 4A and4B. As noted, the display/graphical user interface 404 may provide thedata exchange schemas 302, 304, and/or other schemas associated with auser. Further, the GUI 404 may provide the birthday data 316 and one ormore entities 314 and/or 336 with the access 332 to the birthday data316 based on the access rule 352. Yet further, the GUI 404 may alsoprovide times 416 and/or 418 associated with the access 332 provided tothe entities 314 and/or 336, respectively. For example, the access 332may be provided to the entity 314 at a time 416, possibly based on theuser entering the doctor's office. Further, the access 332 may beprovided to the entity 336 at a time 418, possibly based on the userentering the store described above. As such, the GUI 404 may provide alog of times 416-426 associated with data accesses 332, 334, 338, 340,342, 344, 348, and/or 350 provided to the various entities 314, 336,and/or 346.

As shown, the notification 428 may indicate that there are no rulesassociated with the entity 346 for accessing the browse data 338 and/orthe click data 340. As such, the entity 346 may transfer the browse data338 and/or the click data 340 to second or other entities, possibly withthe external access 358 described above in relation to FIG. 3C-4B. Assuch, the GUI 404 may receive one or more user inputs 414 to set up oneor more rules associated the access 344 of the entity 346 to the browsedata 338 and/or the click data 340.

In addition, the GUI 404 may provide the account data 318 and theentities 314 and/or 336 with access 334 to the account data 318 based onthe access rule 352. Yet further, the GUI 404 may also provide times 416and/or 418 associated with the access 334 provided to the entities 314and/or 336, respectively.

Further, the GUI 404 provides height data 320 and the entity 314 withaccess 338 to the height data 320 based on the access rule 352. Further,the GUI 404 may also provide time 420 associated with the access 338provided to the entity 314. The GUI 404 also provides medical data 322and the entity 314 with access 340 to the medical data 322 based on theaccess rule 352. Further, the GUI 404 may also provide time 420associated with the access 338 provided to the entity 314. For example,access 338 and/or 340 may be provided to the entity 314 at the same time420, possibly based on the user giving the entity 314 permissions toaccess 338 and/or 340 the data 320 and/or 322, respectively.

Yet further, the GUI 404 provides location data 324 and the entity 336with access 342 to the location data 324 based on the access rule 354.Further, the GUI 404 may also provide time 422 associated with theaccess 342 provided to the entity 336. In addition, the GUI 404 providesthe IP address data 326 and the entity 346 with access 348 to the IPaddress data 326 based on the access rule 354. Further, the GUI 404 mayalso provide time 424 associated with the access 348 provided to theentity 346.

Further, the GUI 404 may provide the browse data 328 and one or moreentities 336 and/or 346 with the access 344 to the browse data 328,where the access 344 of the entity 336 is based on the access rule 356.Yet further, the GUI 404 may also provide time 426 associated with theaccess 344 provided to the entities 336 and/or 346, respectively. Yetfurther, the GUI 404 provides click data 330 and the entity 346 withaccess 350 to the click data 330. Further, the GUI 404 may also providetime 426 associated with the access 350 provided to the entity 346.

In some embodiments, the various access rules 352, 354, and/or 356 maybe associated with the data exchange schemas 302 and/or 304. Inparticular, the GUI 404 may provide various permissions of the entities314 and/or 336 to transfer data based on the rule 352. Further, the GUI404 may provide various permission of the entities 336 and/or 346 totransfer data based on the rule 354. Yet further, the GUI 404 mayprovide various permissions of the entity 336 to transfer data based onthe rule 356. As shown, the scroll bar 412 may be used to view otherentities that may have access to data from the data exchange schemas 302and/or 304.

In some embodiments, the smartphone system 400 may notify the userregarding the entities 314, 336, and/or 346 pen fitted to share theuser's data. The smartphone system 400 may perform operations includingdetermining one or more second or other entities that request theportion of the data 316-330 from the one or more entities 314, 336,and/or 346. The operations may include determining the one or moreentities 314, 336, and/or 346 permitted to share the portion of data316-330 to the one or more second or other entities based on one or moreaccess rules 352, 354, and/or 356 determined for the portion of the data316-330. In some instances, the notification 428 transmitted to theclient device 402 may further indicates the one or more entities 314,336, and/or 346 permitted to share the portion of data 316-330 to theone or more second or other entities based on one or more access rules352, 354, and/or 356.

In some embodiments, the smartphone system 400 may perform operationsincluding determining one or more access rules 352, 354, and/or 356associated with the portion of the data 316-330 based on one or moretouch inputs 414 received from the GUI 404 of the client device 402. Theaccesses 332, 334, 338, 340, 342, 344, 348, and/or 350 of the one ormore entities 314, 336, and/or 346 to the portion of the data 316-330may be determined based at least on the one or more rules 352, 354,and/or 356. The operations may also include determining a suggestedchange to the one or more access rules 352, 354, and/or 356 based onsuch accesses of the one or more entities 314, 336, and/or 346 to theportion of the data 316-330, where the notification 428 transmitted tothe client device 402 may further indicate the suggested change to theone or more access rules 352, 354, and/or 356.

In some embodiments, referring back to FIGS. 3A-3C, the data exchangesystem 300 may activate an application, possibly an “app” installed on aclient device. For example, the app may be configured to display the GUI404 shown in FIGS. 4A-4C. Further, the app may be activated to alert theuser with the notification 428. In some instances, the app may providethe one or more suggestions described above to implement rules for theaccesses 344 and/or 350 of the entity 346, among other possibilities.

In some embodiments, the smartphone system 400 may recognize changes tothe data exchange schemas 302, 304, and/or other schemas. For example,the smartphone system 400 may perform operations including determining achange to the portion of data 316-330 accessible by the one or moreentities 314, 336, and/or 346. The operations may also includedetermining a second access or updates to the accesses 332, 334, 338,340, 342, 344, 348, and/or 350 of the one or more entities 314, 336,and/or 346 to the changed portion of data. Further, the notification 428transmitted to the client device 402 may further indicate a request toauthorize the second access of the one or more entities 314, 336, and/or346 to the changed portion of data. As such, user may authorize thesecond access to the changed portion of the data 316-330 accordingly.

FIG. 5 illustrates an exemplary method 500, respectively, according toan embodiment. Notably, one or more steps of the method 500 describedherein may be omitted, performed in a different sequence, and/orcombined with other methods for various types of applicationscontemplated herein.

As shown in FIG. 5, at step 502, the method 500 may include receiving arequest for data from one or more entities. For example, referring backto FIGS. 1A-4C, the method 500 may include the data exchange server 102receiving the request for data from the client device 106 of the one ormore entities. As described above, the request may be embedded in thedata/data packet 124 and received by the data exchange server 102 overthe one or more networks 108 and/or the one or more communicationservers 152.

At step 504, the method 500 may include identifying user data from oneor more data exchange schemas of an account based at least on therequest for the data. For example, referring back to FIGS. 1A-4C, themethod 500 may include one or more hardware processors 112 identifyingthe user data. In particular, as shown in FIGS. 3A-3C, the user data316-330 may be identified from the one or more data exchange schemas 302and/or 304 of an account based on the request for the data.

At step 506, the method 500 may include determining one or more accessrules for the user data determined, where the one or more access rulesare determined based on at least one type of data associated with theuser data requested. For example, referring back to FIGS. 1A-4C, themethod 500 may include the one or more hardware processors 112determining one or more access rules. In particular, as shown in FIGS.3A-3C, the one or more access rules 352, 354, and/or 356, among otheraccess rules described above may be determined.

At step 508, the method 500 may include determining an access of the oneor more entities to the user data based at least on the one or moreaccess rules determined. For example, referring back to FIGS. 1A-4C, themethod 500 may include the one or more hardware processors 112determining the access of the one or more entities. In particular, asshown in FIG. 3C, any one or more of the accesses 332, 334, 338, 340,342, 348, 344, and/or 350 may be determined based on the access rules352, 354, and/or 356, among other access rules described or contemplatedabove.

As noted, the one or more data exchange schemas 302 and/or 304 may bemodified, refined, and/or reformed, possibly over time. For example, thedata exchange schemas 302 and/or 304 may be modified based on the userpurchasing items from a second entity, possibly another merchant store.As such, the method 500 may include the system 300 determining one ormore data transfers with one or more second entities, possibly entitiesother than the entities 314, 336, and/or 346. As such, the one or moredata exchange schemas 302 and/or 304 may be modified based on the one ormore data transfers with the one or more second entities. For example,descriptions of the items, the costs of the items, and/or the quantitiesof the items purchased may be included in the one or more data exchangeschemas 302 and/or 304.

In some embodiments, the user data may change, thereby affecting theaccesses of the one or more entities to the changed user data. Forexample, in some instances, the one or more entities may or may not begiven access to the changed user data. As such, the method 500 mayinclude determining a change to one or more portions of the user data316-330 accessible by the one or more entities 314, 336, and/or 334based at least on the one or more access rules 352, 354, and/or 350determined. Further the method 500 may include determining a secondaccess of the one or more entities 314, 336, and/or 334 to the changeduser data based at least on the access rules 352, 354, and/or 350 forthe user data 316-330.

In some embodiments, the accesses 332, 334, 338, 340, 342, 344, 348,and/or 350 of the one or more entities 314, 336, and/or 346 to the userdata 316-330 indicates one or more permissions of the one or moreentities 314, 336, and/or 346 to share the user data 316-330. The method500 may further include determining a data transfer of the one or moreentities 314, 336, and/or 346 to share the user data 316-330. As noted,the online merchant (e.g., entity 346) may transfer the browse data 328and/or the click data 330 to one or more second or other entities. Assuch, the method 500 may include determining a suggested change to theone or more access rules 352, 354, and/or 356 for the user data 316-330,possibly based on the one or more permissions of the one or moreentities 314, 336, and/or 346 to share the user data 316-330.

FIG. 6 illustrates an exemplary system 600 with a client device 602,according to an embodiment. As shown, the client device 602 may take theform of the client device 402 described above in relation to FIGS.4A-4C. For example, the client device 602 may include a graphical userinterface (GUI) 604 that takes the form of the graphical user interface404. Further, the GUI 604 may provide the data exchange schemas 302,304, and/or other data exchange schemas associated with the user. Yetfurther, the GUI 604 may provide the entities 314 and/or 336 and theirrespective accesses to the data 316, 318, 320, 324, and/or 328. Yetfurther, the GUI 604 may be configured to receive the inputs that maytake the form of the input 414 described above.

As shown, the client device 602 may be in a location 630 shown on thegeographical map 620, shown for illustrative purposes. For example, theclient device 602 may be proximate to the entities 622, 624, 336, and/or628 shown on the geographic map 620 as buildings. In particular, theclient device 602 may be at a location 630 within the building of theentity 336. In some instances, the one or more hardware processors(e.g., the processor 134) of the client device 602 may be configured todetermine the location 630, possibly based on global positioning system(GPS) coordinates of the client device 602.

In some instances, the one or more hardware processors (e.g., processors112 and/or 232) of the system 600 may determine the location 630 byretrieving data from the client device 602. For example, the location630 may be determined by cellular protocol data, including GSM, CDMA,UMTS, EV-DO, WiMAX, or LTE data, and/or base station data, among otherfoams of data possibly available from the one or more data schemas 302and/or 304. In addition, the location 630 may be further determined bysensor data, movement data (e.g., acceleration and/or velocity data) ofthe client device 602, temperature data, radio-frequency identifier(RFID) data, near-field communications (NFC) data, among other possibleforms of data available from the one or more data schemas 302 and/or304.

Referring back to FIG. 5, the method 500 may involve the user receivingnotifications to receive incentives based on sharing data from the oneor more data schemas 302 and/or 304. As shown in FIG. 6, for example,the notification 632 may indicate that the entity 336 would like toshare the user's email address from the account data 318 with the entity628. Further, the entity 336 may offer the user an incentive, such as acoupon, a gift, and/or a complementary item, possibly for sharing theemail address.

For example, the method 500 may include determining an incentiveobtainable from the one or more entities 336 based at least on the oneor more entities 336 being permitted to share the user data, e.g., theemail address from the account data 318, to one or more second entities628. Further, the method 500 may include determining an indication fromthe client device 602 with access to the account to obtain theincentive. For example, the user may provide an input to share the emailaddress to obtain the incentive. As such, the method 500 may includecausing the email address from the user data 318 to be shared with theone or more second entities 628 based at least on the indication fromthe client device 502 to obtain the incentive.

FIG. 7 illustrates an exemplary wearable computing device 700, accordingto an embodiment. As illustrated, the wearable computing device 700 maytake the form of a smart watch. Further, the device 700 may include agraphical user interface (GUI) 704 that may include a smaller version ofthe GUI 604. Yet further, the wearable computing device 700 may includea wrist band 706 that secures around a user's wrist 702. In addition,the wearable computing device 700 may include a number of buttons 708configured to control the GUI 704 and/or sensors 710. The sensors 710,possibly located on the inside surfaces of the wrist band 706, may beconfigured to receive a number of inputs associated with the user. Forexample, the one or more sensors 710 may include accelerometers,gyroscopes, compasses, barometers, capacitive sensors, haptic sensors,temperature sensors, ambient light sensors, sound sensors, imagesensors, biometric sensors, moisture sensors, electrodes, and/orchemical sampling sensors, among other types of sensors to receiveinputs directly and/or indirectly from the user.

As shown, the GUI 704 may provide a notification. For example, referringback to FIG. 5, the method 500 may include transmitting a notificationto the wearable device 700 with access to the user's account. Thenotification may indicate an incentive obtainable from the one or moreentities 332 based at least on the one or more entities 332 beingpermitted to share the email address of the user data, e.g., the accountdata 318, to one or more second entities 628, among various otherpossible types of data.

The present disclosure, the accompanying figures, and the claims are notintended to limit the present disclosure to the example embodimentsdisclosed. As such, it is contemplated that various alternateembodiments and/or modifications to the embodiment disclosed, whetherexplicitly described or implied herein, are possible in light of thedisclosure and/or the figures. Having thus described embodiments of thepresent disclosure, persons of ordinary skill in the art will recognizethat changes may be made to the embodiments disclosed without departingfrom the scope of the present disclosure.

1. A data exchange system, comprising: a non-transitory memory storinginstructions; and one or more hardware processors coupled to thenon-transitory memory and configured to read the instructions to causethe data exchange system to perform operations comprising: determiningone or more data exchange schemas for a user, wherein each data exchangeschema compiles one or more types of data associated with the user;determining a location of a client device of the user, wherein thelocation is associated with one or more entities; in response todetermining the location of the client device, determining at least onedata exchange schema from the one or more data exchange schemas based atleast on the one or more entities; determining an access of the one ormore entities to at least a portion of data from the at least one dataexchange schema; and transmitting a notification to the client devicethat indicates the access of the one or more entities to the portion ofdata from the at least one data exchange schema.
 2. The data exchangesystem of claim 1, wherein the one or more hardware processors isconfigured to read the instructions to cause the data exchange system toperform further operations comprising: determining one or more timesassociated with a user schedule accessible with the client device,wherein the access of the one or more entities to the portion of thedata is determined based at least on the one or more times determined.3. The data exchange system of claim 1, wherein the one or more hardwareprocessors is configured to read the instructions to cause the dataexchange system to perform further operations comprising: receiving oneor more user inputs from a graphical user interface of the client devicethat indicate the one or more types of data, wherein the one or more ofdata exchange schemas are determined based at least on the one or moretypes of data indicated from the one or more user inputs.
 4. The dataexchange system of claim 1, wherein the one or more hardware processorsis configured to read the instructions to cause the data exchange systemto perform further operations comprising: determining a data transfer ofthe one or more types of data based at least on a communication of theclient device with a remote device, wherein the one or more dataexchange schemas is determined based at least on the data transfer ofthe one or more types of data.
 5. The data exchange system of claim 1,wherein the at least one data exchange schema is associated with one ormore access rules determined by the user, and wherein the access of theone or more entities to the portion of data is determined based at leaston a particular access rule from the one or more access rulesdetermined.
 6. The data exchange system of claim 1, wherein the one ormore hardware processors is configured to read the instructions to causethe data exchange system to perform further operations comprising:determining the one or more entities is permitted to share the portionof data based at least on a particular access rule associated with theportion of data; determining one or more second entities that receivethe portion of the data from the one or more entities, wherein thenotification is transmitted to the client device to further indicate theone or more second entities that received the portion of the data. 7.The data exchange system of claim 1, wherein the one or more hardwareprocessors is configured to read the instructions to cause the dataexchange system to perform further operations comprising: determining achange to the portion of data accessible by the one or more entities;determining a second access of the one or more entities to the changedportion of data, wherein the second access of the one or more entitiesis based at least on a particular access rule associated with theportion of data.
 8. The data exchange system of claim 1, wherein theaccess of the one or more entities to the portion of data enables one ormore second entities to access the portion of data based at least on aparticular access rule associated with the portion of the data, whereinthe one or more hardware processors is configured to read theinstructions to cause the data exchange system to perform furtheroperations comprising: determining a suggested change to the particularaccess rule based at least on the one or more second entities withaccess to the portion of data, wherein the notification transmitted tothe client device further indicates the suggested change to theparticular access rule.
 9. A non-transitory machine-readable mediumhaving stored thereon machine-readable instructions executable to causea machine to perform operations comprising: determining one or more dataexchange schemas for a user, wherein each data exchange schema comprisesone or more types of data associated with the user; receiving a requestfrom one or more entities for at least a portion of data from at leastone data exchange schema of the one or more data exchange schemas,wherein the portion of the data comprises at least one a type of datafrom the one or more types of data; in response to receiving the requestfrom the one or more entities, determining an access of the one or moreentities to the portion of data based at least on the type of data ofthe portion of data; and transmitting a notification to a client deviceof the user that indicates the access of the one or more entities to theportion of data.
 10. The non-transitory machine-readable medium of claim9, wherein the machine-readable instructions are executable to cause themachine to perform further operations comprising: determining a datatransfer with a web browser of the client device and a remote serverbased at least on one or more touch inputs received from a graphicaluser interface of the client device, wherein the one or more dataexchange schemas is determined based at least on the data transfer withthe web browser of the client device.
 11. The non-transitorymachine-readable medium of claim 9, wherein the machine-readableinstructions are executable to cause the machine to perform furtheroperations comprising: determining one or more access rules associatedwith the at least one data exchange schema based at least on one or moretouch inputs received from a graphical user interface of the clientdevice, wherein the access of the one or more entities to the portion ofdata is determined based at least on the one or more access rulesdetermined.
 12. The non-transitory machine-readable medium of claim 9,wherein the machine-readable instructions are executable to cause themachine to perform further operations comprising: determining one ormore second entities that request the portion of the data from the oneor more entities; and determining the one or more entities is permittedto share the portion of data to the one or more second entities based atleast on one or more access rules determined for the portion of thedata, wherein the notification transmitted to the client device furtherindicates the one or more entities is permitted to share the portion ofdata to the one or more second entities based at least on one or moreaccess rules.
 13. The non-transitory machine-readable medium of claim 9,wherein the machine-readable instructions are executable to cause themachine to perform further operations comprising: determining a changeto the portion of data accessible by the one or more entities;determining a second access of the one or more entities to the changedportion of data, wherein the notification transmitted to the clientdevice further indicates a request to authorize the second access of theone or more entities to the changed portion of data.
 14. Thenon-transitory machine-readable medium of claim 9, wherein themachine-readable instructions are executable to cause the machine toperform further operations comprising: determining one or more accessrules associated with the portion of the data based at least on one ormore touch inputs received from a graphical user interface of the clientdevice, wherein the access of the one or more entities to the portion ofthe data is determined based at least on the one or more rules; anddetermining a suggested change to the one or more access rules based atleast on the access of the one or more entities to the portion of thedata, wherein the notification transmitted to the client device furtherindicates the suggested change to the one or more access rules.
 15. Amethod to exchange data, comprising: receiving a request for data fromone or more entities; identifying user data from one or more dataexchange schemas of an account based at least on the request for thedata; determining one or more access rules for the user data determined,wherein the one or more access rules are determined based on at leastone type of data associated with the user data requested; anddetermining an access of the one or more entities to the user data basedat least on the one or more access rules determined.
 16. The method ofclaim 15, further comprising determining one or more data transfers withone or more second entities, wherein the one or more data exchangeschemas is modified based at least on the one or more data transferswith the one or more second entities.
 17. The method of claim 15,further comprising: determining a change to the user data accessible bythe one or more entities based at least on the one or more access rulesdetermined; and determining a second access of the one or more entitiesto the changed user data based at least on the one or more access rulesdetermined.
 18. The method of claim 15, wherein the access of the one ormore entities to the user data indicates one or more permissions of theone or more entities to share the user data, the method furthercomprising: determining a data transfer of the one or more entities toshare the user data; determining a suggested change to the one or moreaccess rules for the user data based at least on the one or morepermissions of the one or more entities to share the user data.
 19. Themethod of claim 15, further comprising: determining an incentiveobtainable from the one or more entities based at least on the one ormore entities being permitted to share the user data to one or moresecond entities; determining an indication from a client device withaccess to the account to obtain the incentive; and causing the user datato be shared with the one or more second entities based at least on theindication from the client device to obtain the incentive.
 20. Themethod of claim 15, further comprising transmitting a notification to awearable device with access to the account, wherein the notificationindicates an incentive obtainable from the one or more entities based atleast on the one or more entities being permitted to share the user datato one or more second entities.